<!DOCTYPE HTML>
<html lang="zh-CN">
<head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" /> 
    <title> - 天地维杰网</title>
    <meta name="keywords" content="系统架构,shutdown,不与天斗,Domino,博客,程序员,架构师,笔记,技术,分享,java,Redis">
    
    <meta property="og:title" content="">
    <meta property="og:site_name" content="天地维杰网">
    <meta property="og:image" content="/img/author.jpg"> 
    <meta name="title" content=" - 天地维杰网" />
    <meta name="description" content="天地维杰网 | 博客 | 软件 | 架构 | Java "> 
    <link rel="shortcut icon" href="http://www.shutdown.cn/img/favicon.ico" />
    <link rel="apple-touch-icon" href="http://www.shutdown.cn/img/apple-touch-icon.png" />
    <link rel="apple-touch-icon-precomposed" href="http://www.shutdown.cn/img/apple-touch-icon.png" />
    <link href="http://www.shutdown.cn/js/vendor/font-awesome/css/font-awesome.min.css?v=4.6.2" rel="stylesheet" type="text/css" />
    <link href="http://www.shutdown.cn/js/vendor/fancybox/jquery.fancybox.css?v=2.1.5" rel="stylesheet" type="text/css" />
    <link href="http://www.shutdown.cn/css/main.css" rel="stylesheet" type="text/css" />
    <link href="http://www.shutdown.cn/css/syntax.css" rel="stylesheet" type="text/css" />
    <script type="text/javascript" id="hexo.configuration">
  var NexT = window.NexT || {};
  var CONFIG = {
    scheme: 'Pisces',
    sidebar: {"position":"left","display":"post"},
     fancybox: true, 
    motion: true
  };
</script>
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-7826003325059020" crossorigin="anonymous"></script>
</head>
<body itemscope itemtype="http://schema.org/WebPage" lang="zh-Hans">
<div class="container one-collumn sidebar-position-left page-home  ">
    <div class="headband"></div>

    <header id="header" class="header" itemscope itemtype="http://schema.org/WPHeader">
      <div class="header-inner"> <div class="site-meta  custom-logo ">

  <div class="custom-logo-site-title">
    <a href="http://www.shutdown.cn"  class="brand" rel="start">
      <span class="logo-line-before"><i></i></span>
      <span class="site-title">天地维杰网</span>
      <span class="logo-line-after"><i></i></span>
    </a>
  </div>
  <p class="site-subtitle">人如秋鸿来有信，事若春梦了无痕</p>
</div>

<div class="site-nav-toggle">
  <button>
    <span class="btn-bar"></span>
    <span class="btn-bar"></span>
    <span class="btn-bar"></span>
  </button>
</div>

<nav class="site-nav">
    <ul id="menu" class="menu">
      
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-home"></i> <br />首页
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/redis/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-battery-full"></i> <br />Redis
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/java/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-coffee"></i> <br />java
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/linux/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-linux"></i> <br />linux
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/daily/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-bug"></i> <br />日常问题
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/spring/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-child"></i> <br />Spring和Springboot
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/mac/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-fire"></i> <br />Mac相关
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/middleware/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-gavel"></i> <br />中间件
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/jiagou/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-rocket"></i> <br />架构
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/python/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-ship"></i> <br />python
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/front/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-bolt"></i> <br />前端
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/jvm/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-balance-scale"></i> <br />jvm
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/c/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-battery-empty"></i> <br />c语言
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/categories/web3/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-web3"></i> <br />web3
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/post/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-archive"></i> <br />归档
          </a>
        </li>
      
        <li class="menu-item ">
          <a href="http://www.shutdown.cn/about/" rel="section">
              <i class="menu-item-icon fa fa-fw fa-user"></i> <br />关于
          </a>
        </li>
      
      <li class="menu-item menu-item-search">
        <a href="javascript:;" class="popup-trigger"> <i class="menu-item-icon fa fa-search fa-fw"></i> <br /> 搜索</a>
      </li>
    </ul>
    <div class="site-search">
      <div class="popup">
 <span class="search-icon fa fa-search"></span>
 <input type="text" id="local-search-input">
 <div id="local-search-result"></div>
 <span class="popup-btn-close">close</span>
</div>

    </div>
</nav>

 </div>
    </header>

    <main id="main" class="main">
      <div class="main-inner">
        <div class="content-wrap">
          <div id="content" class="content">
            
<section id="posts" class="posts-expand">
  <article class="post post-type-normal " itemscope itemtype="http://schema.org/Article">
    <header class="post-header">
      <h1 class="post-title" itemprop="name headline">
        <a class="post-title-link" href="http://www.shutdown.cn/post/redis6/" itemprop="url">
        
        </a>
      </h1>
      <div class="post-meta">
      <span class="post-time">
<span class="post-meta-item-icon">
    <i class="fa fa-calendar-o"></i>
</span>
<span class="post-meta-item-text">时间：</span>
<time itemprop="dateCreated" datetime="2016-03-22T13:04:35+08:00" content="0001-01-01">
    0001-01-01
</time>
</span> 
      
      
       <span>
&nbsp; | &nbsp;
<span class="post-meta-item-icon">
    <i class="fa fa-eye"></i>
</span>
<span class="post-meta-item-text">阅读：</span>
<span class="leancloud-visitors-count">4773 字 ~23分钟</span>
</span>
      </div>
    </header>
    <div class="post-body" itemprop="articleBody">
    

    

<h1 id="redis-6-0-release-notes">Redis 6.0 release notes</h1>

<hr />

<p>Upgrade urgency levels:</p>

<p>LOW:      No need to upgrade unless there are new features you want to use.
MODERATE: Program an upgrade of the server, but it&rsquo;s not urgent.
HIGH:     There is a critical bug that may affect a subset of users. Upgrade!
CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
SECURITY: There are security fixes in the release.</p>

<blockquote>
<p>升级紧要级别
LOW : 不需要升级，除非你想要使用新的功能。
MODERATE : 程序升级，但不是紧迫。
HIGH : 有一个严重的bug，可能会影响一些用户。升级！
CRITICAL : 有一个严重的bug，影响大多数用户。立即升级！
SECURITY : 在此版本中有安全修复。</p>
</blockquote>

<h3 id="redis-6-0-16-released-mon-oct-4-12-00-00-idt-2021">Redis 6.0.16 Released Mon Oct 4 12:00:00 IDT 2021</h3>

<p>Upgrade urgency: SECURITY, contains fixes to security issues.</p>

<p>Security Fixes:
* (CVE-2021-41099) Integer to heap buffer overflow handling certain string
  commands and network payloads, when proto-max-bulk-len is manually configured
  to a non-default, very large value [reported by yiyuaner].
* (CVE-2021-32762) Integer to heap buffer overflow issue in redis-cli and
  redis-sentinel parsing large multi-bulk replies on some older and less common
  platforms [reported by Microsoft Vulnerability Research].
* (CVE-2021-32687) Integer to heap buffer overflow with intsets, when
  set-max-intset-entries is manually configured to a non-default, very large
  value [reported by Pawel Wieczorkiewicz, AWS].
* (CVE-2021-32675) Denial Of Service when processing RESP request payloads with
  a large number of elements on many connections.
* (CVE-2021-32672) Random heap reading issue with Lua Debugger [reported by
  Meir Shpilraien].
* (CVE-2021-32628) Integer to heap buffer overflow handling ziplist-encoded
  data types, when configuring a large, non-default value for
  hash-max-ziplist-entries, hash-max-ziplist-value, zset-max-ziplist-entries
  or zset-max-ziplist-value [reported by sundb].
* (CVE-2021-32627) Integer to heap buffer overflow issue with streams, when
  configuring a non-default, large value for proto-max-bulk-len and
  client-query-buffer-limit [reported by sundb].
* (CVE-2021-32626) Specially crafted Lua scripts may result with Heap buffer
  overflow [reported by Meir Shpilraien].</p>

<blockquote>
<p>升级紧急级别，包含安全修复。
安全修复：
* (CVE-2021-41099) 当手动设置proto-max-bulk-len为非默认值，并且为大值时，整数到堆缓冲区溢出处理某些字符串命令和网络负载，[报告于 yiyuaner]。
* (CVE-2021-32762) 在redis-cli和redis-sentinel上，在某些老年和更低频率的平台上，整数到堆缓冲区溢出的问题，[报告于 Microsoft Vulnerability Research]。
* (CVE-2021-32687) 当手动设置set-max-intset-entries为非默认值，并且为非常大的值时，整数到堆缓冲区溢出的问题，[报告于 Pawel Wieczorkiewicz, AWS]。
* (CVE-2021-32675) 在大量连接上处理RESP请求负载时，DoS拒绝服务攻击。
* (CVE-2021-32672) Lua调试器的随机堆读取问题[报告于 Meir Shpilraien]。
* (CVE-2021-32628) 当手动设置hash-max-ziplist-entries、hash-max-ziplist-value、zset-max-ziplist-entries或zset-max-ziplist-value为非默认值，并且为非常大的值时，处理压缩列表编码的数据类型出现整数到堆缓冲区溢出，[报告于 sundb]。
* (CVE-2021-32627) 当手动设置proto-max-bulk-len和client-query-buffer-limit为非默认值，并且为非常大的值时，整数到堆缓冲区溢出的问题，[报告于 sundb]。
* (CVE-2021-32626) 特制的Lua脚本可能导致堆缓冲区溢出[报告于 Meir Shpilraien]。</p>
</blockquote>

<p>Other bug fixes:
* Fix appendfsync to always guarantee fsync before reply, on MacOS and FreeBSD (kqueue) (#9416)
* Fix the wrong mis-detection of sync_file_range system call, affecting performance (#9371)
* Fix replication issues when repl-diskless-load is used (#9280)</p>

<blockquote>
<p>其他bug修复：
* 修复appendfsync在MacOS和FreeBSD上确保fsync在回复之前，[#9416]
* 修复错误的mis-detection of sync_file_range系统调用，影响性能[#9371]
* 修复复制问题，当repl-diskless-load使用时[#9280]</p>
</blockquote>

<h3 id="redis-6-0-15-released-wed-jul-21-16-32-19-idt-2021">Redis 6.0.15 Released Wed Jul 21 16:32:19 IDT 2021</h3>

<p>Upgrade urgency: SECURITY, contains fixes to security issues that affect
authenticated client connections on 32-bit versions. MODERATE otherwise.</p>

<p>Fix integer overflow in BITFIELD on 32-bit versions (CVE-2021-32761).
An integer overflow bug in Redis version 2.2 or newer can be exploited using the
BITFIELD command to corrupt the heap and potentially result with remote code
execution.</p>

<p>Bug fixes that involve behavior changes:
* Change reply type for ZPOPMAX/MIN with count in RESP3 to nested array (#8981).
  Was using a flat array like in RESP2 instead of a nested array like ZRANGE does.</p>

<p>Bug fixes:
* Fail EXEC command in case a watched key is expired (#9194)
* Fix SMOVE not to invalidate dest key (WATCH and tracking) when member already exists (#9244)
* Fix SINTERSTORE not to delete dest key when getting a wrong type error (#9032)
* Fix overflows on 32-bit versions in GETBIT, SETBIT, BITCOUNT, BITPOS, and BITFIELD (#9191)
* Set TCP keepalive on inbound cluster bus connections (#9230)
* Fix ziplist length updates on big-endian platforms (#2080)
* Fix diskless replica loading to recover from RDB short read on module AUX data (#9199)
* Fix race in client side tracking (#9116)
* If diskless repl child is killed, make sure to reap the child pid (#7742)
* Add a timeout mechanism for replicas stuck in fullsync (#8762)</p>

<p>CLI tools:
* redis-cli cluster import support source and target that require auth (#7994)
* redis-cli cluster import command may issue wrong MIGRATE command, sending COPY instead of REPLACE (#8945)
* redis-cli support for RESP3 set type in CSV and RAW output (#7338)</p>

<blockquote>
<p>升级紧急度：SECURITY, 包含修复32位版本上的身份验证客户端连接的安全问题。其余的是MODERATE。</p>

<p>修复32位版本上的BITFIELD中的整数溢出(CVE-2021-32761)。
一个整数溢出bug在Redis版本2.2或更新版本可以通过BITFIELD命令来损坏堆并可能导致远程代码执行。</p>

<p>变化行为的bug修复：
* 修复ZPOPMAX/MIN在RESP3中设置count的回复类型为嵌套数组(#8981)。使用ZRANGE的嵌套数组而不是RESP2的平面数组。</p>

<p>Bug修复：
* 修复EXEC命令在监视的键过期时失败(#9194)
* 修复SMOVE不要在目标键(WATCH和跟踪)已经存在时失效(#9244)
* 修复SINTERSTORE不要在获取错误类型错误时删除目标键(#9032)
* 修复32位版本上的GETBIT,SETBIT,BITCOUNT,BITPOS,和BITFIELD(#9191)
* 设置TCP保持连接在入站集群总线上的连接(#9230)
* 修复ziplist长度在大端平台上更新(#2080)
* 修复磁盘无磁备复制子进程加载RDB短读取模块AUX数据(#9199)
* 如果磁盘无磁备复制子进程被杀死，请确保重新启动子进程(#7742)
* 为复制增加一个超时机制(#8762)</p>

<p>CLI工具：
* redis-cli集群导入支持来源和目标需要身份验证(#7994)
* redis-cli集群导入命令可能发送错误的MIGRATE命令，而不是REPLACE(#8945)
* redis-cli支持RESP3设置类型的CSV和RAW输出(#7338)</p>
</blockquote>

<h3 id="redis-6-0-14-released-tue-june-1-12-00-00-ist-2021">Redis 6.0.14 Released Tue June 1 12:00:00 IST 2021</h3>

<p>Upgrade urgency: SECURITY, Contains fixes to security issues that affect
authenticated client connections. MODERATE otherwise.</p>

<p>Fix integer overflow in STRALGO LCS (CVE-2021-32625)
An integer overflow bug in Redis version 6.0 or newer can be exploited using the
STRALGO LCS command to corrupt the heap and potentially result with remote code
execution. This is a result of an incomplete fix by CVE-2021-29477.</p>

<p>Other bug fixes:
* Fix crash in UNLINK on a stream key with deleted consumer groups (#8932)
* SINTERSTORE: Add missing keyspace del event when none of the sources exist (#8949)</p>

<blockquote>
<p>升级紧急度：SECURITY, 包含修复身份验证客户端连接的安全问题。其余的是MODERATE。</p>

<p>修复整数溢出在STRALGO LCS(CVE-2021-32625)。
一个整数溢出bug在Redis版本6.0或更新版本可以通过STRALGO LCS命令来损坏堆并可能导致远程代码执行。这是由于一个不完整的修复CVE-2021-29477。</p>

<p>其他bug修复：
* 修复在带有删除消费者组的Stream Key(流键)上的使用UNLINK命令造成崩溃的问题(#8932)
* SINTERSTORE: 当没有源时，添加缺少的键空间删除事件(#8949)</p>
</blockquote>

<h3 id="redis-6-0-13-released-mon-may-3-19-00-00-ist-2021">Redis 6.0.13 Released Mon May 3 19:00:00 IST 2021</h3>

<p>Upgrade urgency: SECURITY, Contains fixes to security issues that affect
authenticated client connections. LOW otherwise.</p>

<p>Integer overflow in STRALGO LCS command (CVE-2021-29477):
An integer overflow bug in Redis version 6.0 or newer could be exploited using
the STRALGO LCS command to corrupt the heap and potentially result in remote
code execution. The integer overflow bug exists in all versions of Redis
starting with 6.0.</p>

<p>Integer overflow in COPY command for large intsets (CVE-2021-29478):
An integer overflow bug in Redis 6.2 could be exploited to corrupt the heap and
potentially result with remote code execution. The vulnerability involves
changing the default set-max-intset-entries configuration value, creating a
large set key that consists of integer values and using the COPY command to
duplicate it. The integer overflow bug exists in all versions of Redis starting
with 2.6, where it could result with a corrupted RDB or DUMP payload, but not
exploited through COPY (which did not exist before 6.2).</p>

<p>Bug fixes:
* Cluster: Skip unnecessary check which may prevent failure detection (#8585)
* Fix not starting on alpine/libmusl without IPv6 (#8655)</p>

<p>Improvements:
* Fix performance regression in BRPOP on Redis 6.0 (#8689)</p>

<p>Modules:
* Fix edge-case when a module client is unblocked (#8618)</p>

<blockquote>
<p>升级紧急度：SECURITY, 包含修复身份验证客户端连接的安全问题。其余的是LOW。</p>

<p>修复整数溢出在STRALGO LCS命令(CVE-2021-29477):
一个整数溢出bug在Redis版本6.0或更新版本可以通过STRALGO LCS命令来损坏堆并可能导致远程代码执行。这是由于一个不完整的修复CVE-2021-29478。这个bug存在于所有版本的Redis，从6.0开始。</p>

<p>修复整数溢出在COPY命令中的大intsets(CVE-2021-29478):
一个整数溢出bug在Redis 6.2可以通过COPY命令来损坏堆并可能导致远程代码执行。这个漏洞由于改变默认的set-max-intset-entries配置值，创建一个大的集合键，其中包含整数值，并使用COPY命令来复制它来引发。这个bug存在于所有版本的Redis，从2.6开始，它可能导致一个已损坏的RDB或DUMP负载，但不通过COPY(#8618)。</p>

<p>修复bug：
Cluster: 跳过不必要的检查，这可能会导致故障检测失败(#8585)
修复不启动alpine/libmusl没有IPv6(#8655)</p>

<p>改进：
* 修复BRPOP在Redis 6.0上的性能下降(#8689)</p>

<p>模块：
 * 修复一个模块客户端被解除阻塞的边缘情况(#8618)</p>
</blockquote>

<h3 id="redis-6-0-12-released-mon-mar-1-17-29-52-ist-2021">Redis 6.0.12     Released Mon Mar  1 17:29:52 IST 2021</h3>

<p>Upgrade urgency: LOW, fixes a compilation issue.</p>

<p>Bug fixes:
* Fix compilation error on non-glibc systems if jemalloc is not used (#8533)</p>

<blockquote>
<p>升级紧急度：LOW, 修复编译错误。</p>

<p>修复bug：
* 修复在非glibc系统上，如果没有使用jemalloc，则编译错误(#8533)</p>
</blockquote>

<h3 id="redis-6-0-11-released-mon-feb-22-16-13-23-ist-2021">Redis 6.0.11     Released Mon Feb 22 16:13:23 IST 2021</h3>

<p>Upgrade urgency: SECURITY if you use 32bit build of redis (see bellow), LOW
otherwise.</p>

<p>Integer overflow on 32-bit systems (CVE-2021-21309):
Redis 4.0 or newer uses a configurable limit for the maximum supported bulk
input size. By default, it is 512MB which is a safe value for all platforms.
If the limit is significantly increased, receiving a large request from a client
may trigger several integer overflow scenarios, which would result with buffer
overflow and heap corruption.</p>

<p>Bug fixes:
* Avoid 32-bit overflows when proto-max-bulk-len is set high (#8522)
* Fix handling of threaded IO and CLIENT PAUSE (failover), could lead to data loss or a crash (#8520)
* Fix the selection of a random element from large hash tables (#8133)
* Fix broken protocol in client tracking tracking-redir-broken message (#8456)
* XINFO able to access expired keys on a replica (#8436)
* Fix broken protocol in redis-benchmark when used with -a or &ndash;dbnum (#8486)
* Avoid assertions (on older kernels) when testing arm64 CoW bug (#8405)
* CONFIG REWRITE should honor umask settings (#8371)
* Fix firstkey,lastkey,step in COMMAND command for some commands (#8367)</p>

<p>Modules:
* RM_ZsetRem: Delete key if empty, the bug could leave empty zset keys (#8453)</p>

<blockquote>
<p>升级紧急度：如果您使用32位编译的redis，则SECURITY，否则LOW。</p>

<p>修复整数溢出在32位系统上(CVE-2021-21309)：
Redis 4.0或更新版本可以通过配置来限制最大的批量输入大小。默认情况下，它是512MB，这是一个安全值对所有平台。如果限制被增大，接收一个客户端的大请求可能会触发几个整数溢出情况，这可能会导致缓冲区溢出和堆垃圾。</p>

<p>修复bug：
* 避免32位溢出，当proto-max-bulk-len设置高(#8522)
* 修复处理线程IO和CLIENT PAUSE (failover)，可能导致数据丢失或崩溃(#8520)
* 修复选择随机元素的大哈希表(#8133)
* 修复客户端跟踪trace-redir-broken消息的协议(#8456)
* XINFO能访问过期键的副本(#8436)
* 修复redis-benchmark使用-a或&ndash;dbnum时的协议(#8486)
* 避免断言(on older kernels)，当测试arm64 CoW bug(#8405)
* CONFIG REWRITE应该遵循umask设置(#8371)
* 修复firstkey,lastkey,step在COMMAND命令中的某些命令(#8367)</p>

<p>模块：
* RM_ZsetRem: 如果空，删除键，这个bug可能会留下空zset键(#8453)</p>
</blockquote>

<h3 id="redis-6-0-10-released-tue-jan-12-16-20-20-ist-2021">Redis 6.0.10     Released Tue Jan 12 16:20:20 IST 2021</h3>

<p>Upgrade urgency MODERATE: several bugs with moderate impact are fixed,
Here is a comprehensive list of changes in this release compared to 6.0.9.</p>

<p>Command behavior changes:
* SWAPDB invalidates WATCHed keys (#8239)
* SORT command behaves differently when used on a writable replica (#8283)
* EXISTS should not alter LRU (#8016)
  In Redis 5.0 and 6.0 it would have touched the LRU/LFU of the key.
* OBJECT should not reveal logically expired keys (#8016)
  Will now behave the same TYPE or any other non-DEBUG command.
* GEORADIUS[BYMEMBER] can fail with -OOM if Redis is over the memory limit (#8107)</p>

<p>Other behavior changes:
* Sentinel: Fix missing updates to the config file after SENTINEL SET command (#8229)
* CONFIG REWRITE is atomic and safer, but requires write access to the config file&rsquo;s folder (#7824, #8051)
  This change was already present in 6.0.9, but was missing from the release notes.</p>

<p>Bug fixes with compatibility implications (bugs introduced in Redis 6.0):
* Fix RDB CRC64 checksum on big-endian systems (#8270)
  If you&rsquo;re using big-endian please consider the compatibility implications with
  RESTORE, replication and persistence.
* Fix wrong order of key/value in Lua&rsquo;s map response (#8266)
  If your scripts use redis.setresp() or return a map (new in Redis 6.0), please
  consider the implications.</p>

<p>Bug fixes:
* Fix an issue where a forked process deletes the parent&rsquo;s pidfile (#8231)
* Fix crashes when enabling io-threads-do-reads (#8230)
* Fix a crash in redis-cli after executing cluster backup (#8267)
* Handle output buffer limits for module blocked clients (#8141)
  Could result in a module sending reply to a blocked client to go beyond the limit.
* Fix setproctitle related crashes. (#8150, #8088)
  Caused various crashes on startup, mainly on Apple M1 chips or under instrumentation.
* Backup/restore cluster mode keys to slots map for repl-diskless-load=swapdb (#8108)
  In cluster mode with repl-diskless-load, when loading failed, slot map wouldn&rsquo;t
  have been restored.
* Fix oom-score-adj-values range, and bug when used in config file (#8046)
  Enabling setting this in the config file in a line after enabling it, would
  have been buggy.
* Reset average ttl when empty databases (#8106)
  Just causing misleading metric in INFO
* Disable rehash when Redis has child process (#8007)
  This could have caused excessive CoW during BGSAVE, replication or AOFRW.
* Further improved ACL algorithm for picking categories (#7966)
  Output of ACL GETUSER is now more similar to the one provided by ACL SETUSER.
* Fix bug with module GIL being released prematurely (#8061)
  Could in theory (and rarely) cause multi-threaded modules to corrupt memory.
* Reduce effect of client tracking causing feedback loop in key eviction (#8100)
* Fix cluster access to unaligned memory (SIGBUS on old ARM) (#7958)
* Fix saving of strings larger than 2GB into RDB files (#8306)</p>

<p>Additional improvements:
* Avoid wasteful transient memory allocation in certain cases (#8286, #5954)</p>

<p>Platform / toolchain support related improvements:
* Fix crash log registers output on ARM. (#8020)
* Add a check for an ARM64 Linux kernel bug (#8224)
  Due to the potential severity of this issue, Redis will print log warning on startup.
* Raspberry build fix. (#8095)</p>

<p>New configuration options:
* oom-score-adj-values config can now take absolute values (besides relative ones) (#8046)</p>

<p>Module related fixes:
* Moved RMAPI_FUNC_SUPPORTED so that it&rsquo;s usable (#8037)
* Improve timer accuracy (#7987)
* Allow &lsquo;\0&rsquo; inside of result of RM_CreateStringPrintf (#6260)</p>

<blockquote>
<p>升级紧急 MODERATE: 修复了几个有中级影响的bug，与6.0.9版本相比，这次的升级有一些综合的变更。</p>

<p>命令行为变更：
* <code>SWAPDB</code> 命令作废 WATCHed 键 (#8239)
* <code>SORT</code> 命令行为变更，当使用在可写副本上时 (#8283)
* <code>EXISTS</code> 不会改变 LRU (#8016)
  在 Redis 5.0 和 6.0 中，它会对键的<code>LRU/LFU</code>进行修改。
* OBJECT 不会展示逻辑过期的键 (#8016)
  将会行为与任何非DEBUG命令相同。
* GEORADIUS[BYMEMBER] 可能会在oom时失败 (#8107)
其他行为变更：
* Sentinel: 修复使用<code>SENTINEL SET</code>命令后未对配置文件的更新的问题(#8229)
* CONFIG REWRITE 是原子的和安全的，但是需要写入配置文件的文件夹 (#7824, #8051)
 这次的升级已经在6.0.9中存在，但是在发布日志中没有出现。</p>

<p>兼容性bug修复（Redis 6.0中新增的bug）：
* 修复RDB CRC64校验和在big-endian大端系统上的问题 (#8270)
  如果你使用big-endian大端系统，请考虑兼容性问题与备份、复制和持久化。
* 修复Lua的map回复中的键值顺序 (#8266)
  如果你的脚本使用redis.setresp()或返回一个map（新在Redis 6.0中），请考虑兼容性问题。</p>

<p>Bug修复：
* 修复forked进程删除父进程的pid文件的问题 (#8231)
* 修复io-threads-do-reads的问题 (#8230)
* 修复redis-cli执行cluster backup后崩溃的问题 (#8267)
* 修复模块的输出缓冲区限制（＃8141）
  可能导致模块发送回复给阻止客户端的缓冲区超过限制。
* 修复setproctitle（设置进程名的python模块）相关的崩溃（#8150，#8088）
  导致多种启动崩溃，主要是在Apple M1芯片或者设备上。
* 备份/恢复 cluster模式的keys到槽位map
    Backup/restore cluster mode keys to slots map for repl-diskless-load=swapdb (#8108)
    In cluster mode with repl-diskless-load, when loading failed, slot map wouldn&rsquo;t
    have been restored.</p>
</blockquote>

<h3 id="redis-6-0-9-released-mon-oct-26-10-37-47-ist-2020">Redis 6.0.9     Released Mon Oct 26 10:37:47 IST 2020</h3>

<p>Upgrade urgency: SECURITY if you use an affected platform (see below).
                 Otherwise the upgrade urgency is MODERATE.</p>

<p>This release fixes a potential heap overflow when using a heap allocator other
than jemalloc or glibc&rsquo;s malloc. See:
<a href="https://github.com/redis/redis/pull/7963">https://github.com/redis/redis/pull/7963</a></p>

<p>Other fixes in this release:</p>

<p>New:
* Memory reporting of clients argv (#7874)
* Add redis-cli control on raw format line delimiter (#7841)
* Add redis-cli support for rediss:// -u prefix (#7900)
* Get rss size support for NetBSD and DragonFlyBSD</p>

<p>Behavior changes:
* WATCH no longer ignores keys which have expired for MULTI/EXEC (#7920)
* Correct OBJECT ENCODING response for stream type (#7797)
* Allow blocked XREAD on a cluster replica (#7881)
* TLS: Do not require CA config if not used (#7862)</p>

<p>Bug fixes:
* INFO report real peak memory (before eviction) (#7894)
* Allow requirepass config to clear the password (#7899)
* Fix config rewrite file handling to make it really atomic (#7824)
* Fix excessive categories being displayed from ACLs (#7889)
* Add fsync in replica when full RDB payload was received (#7839)
* Don&rsquo;t write replies to socket when output buffer limit reached (#7202)
* Fix redis-check-rdb support for modules aux data (#7826)
* Other smaller bug fixes</p>

<p>Modules API:
* Add APIs for version and compatibility checks (#7865)
* Add RM_GetClientCertificate (#7866)
* Add RM_GetDetachedThreadSafeContext (#7886)
* Add RM_GetCommandKeys (#7884)
* Add Swapdb Module Event (#7804)
* RM_GetContextFlags provides indication of being in a fork child (#7783)
* RM_GetContextFlags document missing flags: MULTI_DIRTY, IS_CHILD (#7821)
* Expose real client on connection events (#7867)
* Minor improvements to module blocked on keys (#7903)</p>

<p>================================================================================</p>

<h1 id="redis-6-0-8-released-wed-sep-09-23-34-17-idt-2020">Redis 6.0.8     Released Wed Sep 09 23:34:17 IDT 2020</h1>

<p>Upgrade urgency HIGH: Anyone who&rsquo;s using Redis 6.0.7 with Sentinel or
CONFIG REWRITE command is affected and should upgrade ASAP, see #7760.</p>

<p>Bug fixes:</p>

<ul>
<li>CONFIG REWRITE after setting oom-score-adj-values either via CONFIG SET or
loading it from a config file, will generate a corrupt config file that will
cause Redis to fail to start</li>
<li>Fix issue with redis-cli &ndash;pipe on MacOS</li>
<li>Fix RESP3 response for HKEYS/HVALS on non-existing key</li>
<li>Various small bug fixes</li>
</ul>

<p>New features / Changes:</p>

<ul>
<li>Remove THP warning when set to madvise</li>
<li>Allow EXEC with read commands on readonly replica in cluster</li>
<li>Add masters/replicas options to redis-cli &ndash;cluster call command</li>
</ul>

<p>Module API:</p>

<ul>
<li>Add RedisModule_ThreadSafeContextTryLock</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-7-released-fri-aug-28-11-05-09-idt-2020">Redis 6.0.7     Released Fri Aug 28 11:05:09 IDT 2020</h1>

<p>Upgrade urgency MODERATE: several bugs with moderate impact are fixed,
Specifically the first two listed below which cause protocol errors for clients.</p>

<p>Bug fixes:</p>

<ul>
<li>CONFIG SET could hung the client when arrives during RDB/ROF loading (When
processed after another command that was also rejected with -LOADING error)</li>
<li>LPOS command when RANK is greater than matches responded wiht broken protocol
(negative multi-bulk count)</li>
<li>UNLINK / Lazyfree for stream type key would have never do async freeing</li>
<li>PERSIST should invalidate WATCH (Like EXPIRE does)</li>
<li>EXEC with only read commands could have be rejected when OOM</li>
<li>TLS: relax verification on CONFIG SET (Don&rsquo;t error if some configs are set
and tls isn&rsquo;t enabled)</li>
<li>TLS: support cluster/replication without tls-port</li>
<li>Systemd startup after network is online</li>
<li>Redis-benchmark improvements</li>
<li>Various small bug fixes</li>
</ul>

<p>New features:</p>

<ul>
<li>Add oom-score-adj configuration option to control Linux OOM killer</li>
<li>Show IO threads statistics and status in INFO output</li>
<li>Add optional tls verification mode (see tls-auth-clients)</li>
</ul>

<p>Module API:</p>

<ul>
<li>Add RedisModule_HoldString</li>
<li>Add loaded keyspace event</li>
<li>Fix RedisModuleEvent_LoadingProgress</li>
<li>Fix RedisModuleEvent_MasterLinkChange hook missing on successful psync</li>
<li>Fix missing RM_CLIENTINFO_FLAG_SSL</li>
<li>Refactor redismodule.h for use with -fno-common / extern</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-6-released-mon-jul-20-09-31-30-idt-2020">Redis 6.0.6     Released Mon Jul 20 09:31:30 IDT 2020</h1>

<p>Upgrade urgency MODERATE: several bugs with moderate impact are fixed here.</p>

<p>The most important issues are listed here:</p>

<ul>
<li>Fix crash when enabling CLIENT TRACKING with prefix</li>
<li>EXEC always fails with EXECABORT and multi-state is cleared</li>
<li>RESTORE ABSTTL won&rsquo;t store expired keys into the db</li>
<li>redis-cli better handling of non-pritable key names</li>
<li>TLS: Ignore client cert when tls-auth-clients off</li>
<li>Tracking: fix invalidation message on flush</li>
<li>Notify systemd on Sentinel startup</li>
<li>Fix crash on a misuse of STRALGO</li>
<li>Few fixes in module API</li>
<li>Fix a few rare leaks (STRALGO error misuse, Sentinel)</li>
<li>Fix a possible invalid access in defrag of scripts (unlikely to cause real harm)</li>
</ul>

<p>New features:</p>

<ul>
<li>LPOS command to search in a list</li>
<li>Use user+pass for MIGRATE in redis-cli and redis-benchmark in cluster mode</li>
<li>redis-cli support TLS for &ndash;pipe, &ndash;rdb and &ndash;replica options</li>
<li>TLS: Session caching configuration support</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-5-released-tue-jun-09-11-56-08-cest-2020">Redis 6.0.5     Released Tue Jun 09 11:56:08 CEST 2020</h1>

<p>Upgrade urgency MODERATE: several bugs with moderate impact are fixed here.</p>

<p>The most important issues are listed here:</p>

<ul>
<li>Fix handling of speical chars in ACL LOAD.</li>
<li>Make Redis Cluster more robust about operation errors that may lead
to two clusters to mix together.</li>
<li>Revert the sendfile() implementation of RDB transfer. It causes some delay.</li>
<li>Fix TLS certificate loading for chained certificates.</li>
<li>Fix AOF rewirting of KEEPTTL SET option.</li>
<li>Fix MULTI/EXEC behavior during -BUSY script errors.</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-4-released-thu-may-28-11-36-45-cest-2020">Redis 6.0.4     Released Thu May 28 11:36:45 CEST 2020</h1>

<p>Upgrade urgency CRITICAL: this release fixes a severe replication bug.</p>

<p>Redis 6.0.4 fixes a critical replication bug caused by a new feature introduced
in Redis 6. The feature, called &ldquo;meaningful offset&rdquo; and strongly wanted by
myself (antirez) was an improvement that avoided that masters were no longer
able, during a failover where they were demoted to replicas, to partially
synchronize with the new master. In short the feature was able to avoid full
synchronizations with RDB. How did it work? By trimming the replication backlog
of the final &ldquo;PING&rdquo; commands the master was sending in the replication channel:
this way the replication offset would no longer go &ldquo;after&rdquo; the one of the
promoted replica, allowing the master to just continue in the same replication
history, receiving only a small data difference.</p>

<p>However after the introduction of the feature we (the Redis core team) quickly
understood there was something wrong: the apparently harmless feature had
many bugs, and the last bug we discovered, after a joined effort of multiple
people, we were not even able to fully understand after fixing it. Enough was
enough, we decided that the complexity cost of this feature was too high.
So Redis 6.0.4 removes the feature entirely, and fixes the data corruption that
it was able to cause.</p>

<p>However there are two facts to take in mind.</p>

<p>Fact 1: Setups using chained replication, that means that certain replicas
are replicating from other replicas, up to Redis 6.0.3 can experience data
corruption. For chained replication we mean that:</p>
<div class="highlight"><pre style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-fallback" data-lang="fallback">+--------+          +---------+         +-------------+
| master |---------&gt;| replica |--------&gt;| sub-replica |
+--------+          +---------+         +-------------+</code></pre></div>
<p>People using chained replication SHOULD UPGRADE ASAP away from Redis 6.0.0,
6.0.1, 6.0.2 or 6.0.3 to Redis 6.0.4.</p>

<p>To be clear, people NOT using this setup, but having just replicas attached
directly to the master, SHOUDL NOT BE in danger of any problem. But we
are no longer confident on 6.0.x replication implementation complexities
so we suggest to upgrade to 6.0.4 to everybody using an older 6.0.3 release.
We just so far didn&rsquo;t find any bug that affects Redis 6.0.3 that does not
involve chained replication.</p>

<p>People starting with Redis 6.0.4 are fine. People with Redis 5 are fine.
People upgrading from Redis 5 to Redis 6.0.4 are fine.
TLDR: The problem is with users of 6.0.0, 6.0.1, 6.0.2, 6.0.3.</p>

<p>Fact 2: Upgrading from Redis 6.0.x to Redis 6.0.4, IF AND ONLY IF you
use chained replication, requires some extra care:</p>

<ol>
<li><p>Once you attach your new Redis 6.0.4 instance as a replica of the current
Redis 6.0.x master, you should wait for the first full synchronization,
then you should promote it right away, if your setup involves chained
replication. Don&rsquo;t give it the time to do a new partial synchronization
in the case the link between the master and the replica  will break in
the mean time.</p></li>

<li><p>As an additional care, you may want to set the replication ping period
to a very large value (for instance 1000000) using the following command:</p>

<p>CONFIG SET repl-ping-replica-period 1000000</p></li>
</ol>

<p>Note that if you do &ldquo;1&rdquo; with care, &ldquo;2&rdquo; is not needed.
   However if you do it, make sure to later restore it to its default:</p>
<div class="highlight"><pre style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-fallback" data-lang="fallback">   CONFIG SET repl-ping-replica-period 10</code></pre></div>
<p>So this is the main change in Redis 6. Later we&rsquo;ll find a different way in
order to achieve what we wanted to achieve with the Meaningful Offset feature,
but without the same complexity.</p>

<p>Other changes in this release:</p>

<ul>
<li>PSYNC2 tests improved.</li>
<li>Fix a rare active defrag edge case bug leading to stagnation</li>
<li>Fix Redis 6 asserting at startup in 32 bit systems.</li>
<li>Redis 6 32 bit is now added back to our testing environments.</li>
<li>Fix server crash for STRALGO command,</li>
<li>Implement sendfile for RDB transfer.</li>
<li>TLS fixes.</li>
<li>Make replication more resistant by disconnecting the master if we
detect a protocol error. Basically we no longer accept inline protocol
from the master.</li>
<li>Other improvements in the tests.</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-3-released-sat-may-16-18-10-21-cest-2020">Redis 6.0.3     Released Sat May 16 18:10:21 CEST 2020</h1>

<p>Upgrade urgency CRITICAL: a crash introduced in 6.0.2 is now fixed.</p>

<p>1eab62f7e Remove the client from CLOSE_ASAP list before caching the master.</p>

<p>================================================================================</p>

<h1 id="redis-6-0-2-released-fri-may-15-22-24-36-cest-2020">Redis 6.0.2     Released Fri May 15 22:24:36 CEST 2020</h1>

<p>Upgrade urgency MODERATE: many not critical bugfixes in different areas.
                          Critical fix to client side caching when
                          keys are evicted from the tracking table but
                          no notifications are sent.</p>

<p>The following are the most serious fix:</p>

<ul>
<li>XPENDING should not update consumer&rsquo;s seen-time</li>
<li>optimize memory usage of deferred replies - fixed</li>
<li>Fix CRC64 initialization outside the Redis server itself.</li>
<li>stringmatchlen() should not expect null terminated strings.</li>
<li>Cluster nodes availability checks improved when there is
high Pub/Sub load on the cluster bus.</li>
<li>Redis Benchmark: Fix coredump because of double free</li>
<li>Tracking: send eviction messages when evicting entries.</li>
<li>rax.c updated from upstream antirez/rax.</li>
<li>fix redis 6.0 not freeing closed connections during loading.</li>
</ul>

<p>New features:</p>

<ul>
<li>Support setcpuaffinity on linux/bsd</li>
<li>Client Side Caching: Add Tracking Prefix Number Stats in Server Info</li>
<li>Add &ndash;user argument to redis-benchmark.c (ACL)</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-1-released-sat-may-02-00-06-07-cest-2020">Redis 6.0.1     Released Sat May 02 00:06:07 CEST 2020</h1>

<p>Upgrade urgency HIGH: This release fixes a crash when builiding against
                      Libc malloc.</p>

<p>Here we revert 8110ba888, an optimization that causes a crash due to a
bug in the code. It does not happen with the default allocator because of
differences between Jemalloc and libc malloc, so this escaped all our
testing but was reported by a user. We&rsquo;ll add back the original optimization
that was reverted here later, after checking what happens: it is not a
critical optimization.</p>

<p>================================================================================</p>

<h1 id="redis-6-0-0-ga-released-thu-apr-30-14-55-02-cest-2020">Redis 6.0.0 GA  Released Thu Apr 30 14:55:02 CEST 2020</h1>

<p>Upgrade urgency CRITICAL: many bugs fixed compared to the last release
                          candidate. Better to upgrade if you see things
                          affecting your environment in the changelog.</p>

<p>Hi all, finally we have Redis 6.0.0 GA! Enjoy this new Redis release.
Most of the documentation was updated today so that you can likely
find what you are looking for about the new features at redis.io.
This is the list of what changed compared to the previoius release candidate:</p>

<ul>
<li>XCLAIM AOF/replicas propagation fixed.</li>
<li>Client side caching: new NOLOOP option to avoid getting notified about
changes performed by ourselves.</li>
<li>ACL GENPASS now uses HMAC-SHA256 and have an optional &ldquo;bits&rdquo; argument.
It means you can use it as a general purpose &ldquo;secure random strings&rdquo;
primitive!</li>
<li>Cluster &ldquo;SLOTS&rdquo; subcommand memory optimization.</li>
<li>The LCS command is now a subcommand of STRALGO.</li>
<li>Meaningful offset for replicas as well. More successful partial
resynchronizations.</li>
<li>Optimize memory usage of deferred replies.</li>
<li>Faster CRC64 algorithm for faster RDB loading.</li>
<li>XINFO STREAM FULL, a new subcommand to get the whole stream state.</li>
<li>CLIENT KILL USER <username>.</li>
<li>MIGRATE AUTH2 option, for ACL style authentication support.</li>
<li>Other random bugfixes.</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-rc4-released-thu-apr-16-16-10-35-cest-2020">Redis 6.0-rc4     Released Thu Apr 16 16:10:35 CEST 2020</h1>

<p>Upgrade urgency LOW: If you are using RC3 without issues, don&rsquo;t rush.</p>

<p>Hi all, this the latest release candidate of Redis 6. This is likely to
be very similar to what you&rsquo;ll see in Redis 6 GA. Please test it and
report any issue :-)</p>

<p>Main changes in this release:</p>
<div class="highlight"><pre style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-fallback" data-lang="fallback">* Big INFO speedup when using a lot of of clients.
* Big speedup on all the blocking commands: now blocking
  on the same key is O(1) instead of being O(N).
* Stale replicas now allow MULTI/EXEC.
* New command: LCS (Longest Common Subsequence).
* Add a new configuration to make DEL like UNLINK.
* RDB loading speedup.
* Many bugs fixed (see the commit messages at the end of this node)</code></pre></div>
<p>================================================================================</p>

<h1 id="redis-6-0-rc3-released-tue-mar-31-17-42-39-cest-2020">Redis 6.0-rc3     Released Tue Mar 31 17:42:39 CEST 2020</h1>

<p>Upgrade urgency CRITICAL: A connection management bug introduced with the
                          SSL implementation can crash Redis easily.</p>

<p>Dear users, this is a list of the major changes in this release, please check
the list of commits for detail:</p>

<ul>
<li>Fix crash due to refactoring for SSL, for the connection code.</li>
<li>Precise timeouts for blocking commands. Now the timeouts have HZ
resolution regardless of the number of connected clinets. New timeouts
are stored in a radix tree and sorted by expire time.</li>
<li>Fix rare crash when resizing the event loop because of CONFIG maxclients.</li>
<li>Fix systemd readiness after successful partial resync.</li>
<li>Redis-cli ask password mode to be prompted at startup (for additional safety).</li>
<li>Keyspace notifications added to MIGRATE / RESTORE.</li>
<li>Threaded I/O bugs fixed.</li>
<li>Implement new ACL style AUTH in Sentinel.</li>
<li>Make &lsquo;requirepass&rsquo; more backward compatible with Redis &lt;= 5.</li>
<li>ACL: Handle default user as disabled if it&rsquo;s off regardless of &ldquo;nopass&rdquo;.</li>
<li>Fix a potential inconsistency when upgrading an instance in Redis Cluster
and restarting it. The instance will act as a replica but will actually be
set as a master immediately. However the choice of what to do with already
expired keys, on loading, was made from the POV of replicas.</li>
<li>Abort transactions after -READONLY error.</li>
<li>Many different fixes to module APIs.</li>
<li>BITFIELD_RO added to call the command on read only replicas.</li>
<li>PSYNC2: meaningful offset implementation. Allow the disconnected master
that is still sending PINGs to replicas, to be able to successfully
PSYNC incrementally to new slaves, discarding the last part of the
replication backlog consisting only of PINGs.</li>
<li>Fix pipelined MULTI/EXEC during Lua scripts are in BUSY state.</li>
<li>Re-fix propagation API in modules, broken again after other changes.</li>
</ul>

<p>================================================================================</p>

<h1 id="redis-6-0-rc1-released-thu-dec-19-09-58-24-cest-2019">Redis 6.0 RC1   Released Thu Dec 19 09:58:24 CEST 2019</h1>

<p>Upgrade urgency LOW: This is the first RC of Redis 6.</p>

<h1 id="introduction-to-the-redis-6-release">Introduction to the Redis 6 release</h1>

<p>Redis 6 improves Redis in a number of key areas and is one of the largest
Redis releases in the history of the project, so here we&rsquo;ll list only
the biggest features in this release:</p>

<ul>
<li>The modules system now has a number of new APIs that allow module authors
to make things otherwise not possible in the past. It is possible to
store arbitrary module private data in RDB files, to hook on different
server events, capture and rewrite commands executions, block clients on
keys, and so forth.</li>
<li>The Redis active expire cycle was rewritten for much faster eviction of keys
that are already expired. Now the effort is tunable.</li>
<li>Redis now supports SSL on all channels.</li>
<li>ACL support, you can define users that can run only certain commands and/or
can only access only certain keys patterns.</li>
<li>Redis now supports a new protocol called RESP3, which returns more
semantical replies: new clients using this protocol can understand just
from the reply what type to return to the calling program.</li>
<li>There is server-side support for client-side caching of key values. This
feature is still experimental and will get more changes during the next
release candidates, but you can already test it and read about it here:
<a href="https://redis.io/topics/client-side-caching">https://redis.io/topics/client-side-caching</a></li>
<li>Redis can now optionally use threads to handle I/O, allowing to serve
2 times as much operations per second in a single instance when
pipelining cannot be used.</li>
<li>Diskless replication is now supported even on replicas: a replica is now
able, under certain conditions the user can configure, to load the RDB
in the first synchronization directly from the socket to the memory.</li>
<li>Redis-benchmark now supports a Redis Cluster mode.</li>
<li>SRANDMEMBER and similar commands have a better distribution.</li>
<li>Redis-cli improvements.</li>
<li>Systemd support rewritten.</li>
<li>A Redis Cluster proxy was released here:
<a href="https://github.com/artix75/redis-cluster-proxy">https://github.com/artix75/redis-cluster-proxy</a></li>
<li>A Disque module for Redis was released here:
<a href="https://github.com/antirez/disque-module">https://github.com/antirez/disque-module</a></li>
</ul>

<p>Redis 6.0 is mostly a strict superset of 5.0, you should not have any problem
upgrading your application from 5.0 to 6.0. However this is a list of small
non-backward compatible changes introduced in the 6.0 release:</p>

<ul>
<li>The SPOP <count> command no longer returns null when the set key does not
exist. Now it returns the empty set as it should and as happens when it is
called with a 0 argument. This is technically a fix, however it changes the
old behavior.</li>
</ul>

<hr />

<p>Credits: For each release, a list of changes with the relative author is
provided. Where not specified the implementation and design is done by
Salvatore Sanfilippo. Thanks to Redis Labs for making all this possible.
Also many thanks to all the other contributors and the amazing community
we have.</p>

    </div>
    <footer class="post-footer">
     

     <div class="post-nav">
    <div class="post-nav-next post-nav-item">
    
        <a href="http://www.shutdown.cn/post/redis6.2%E7%89%88%E6%9C%AC%E4%BB%8B%E7%BB%8D/" rel="next" title="">
        <i class="fa fa-chevron-left"></i> 
        </a>
    
    </div>

    <div class="post-nav-prev post-nav-item">
    
        <a href="http://www.shutdown.cn/post/redis6%E7%94%9F%E4%BA%A7%E9%85%8D%E7%BD%AE/" rel="prev" title="">
         <i class="fa fa-chevron-right"></i>
        </a>
    
    </div>
</div>
      
     
     
     






    </footer>
  </article>
</section>

          </div>
        </div>
        <div class="sidebar-toggle">
  <div class="sidebar-toggle-line-wrap">
    <span class="sidebar-toggle-line sidebar-toggle-line-first"></span>
    <span class="sidebar-toggle-line sidebar-toggle-line-middle"></span>
    <span class="sidebar-toggle-line sidebar-toggle-line-last"></span>
  </div>
</div>
<aside id="sidebar" class="sidebar">
  <div class="sidebar-inner">

    <section class="site-overview sidebar-panel  sidebar-panel-active ">
      <div class="site-author motion-element" itemprop="author" itemscope itemtype="http://schema.org/Person">
    <img class="site-author-image" itemprop="image"
        src="http://www.shutdown.cn/img/author.jpg"
        alt="不与天斗Domino" />
    <p class="site-author-name" itemprop="name">不与天斗Domino</p>
    <p class="site-description motion-element" itemprop="description"> 
        Programmer &amp; Architect</p>
</div>
      <nav class="site-state motion-element">
    <div class="site-state-item site-state-posts">
      <a href="http://www.shutdown.cn/post/">
        <span class="site-state-item-count">183</span>
        <span class="site-state-item-name">日志</span>
      </a>
    </div>
    <div class="site-state-item site-state-categories">    
        <a href="http://www.shutdown.cn/categories/">      
         
        <span class="site-state-item-count">15</span>
        
        <span class="site-state-item-name">分类</span>
        
        </a>
    </div>

    <div class="site-state-item site-state-tags">
        <a href="http://www.shutdown.cn/tags/">
         
        <span class="site-state-item-count">224</span>
        
        <span class="site-state-item-name">标签</span>
        </a>
    </div>
</nav>
      
      

      

      <div class="links-of-blogroll motion-element inline">
<script type="text/javascript" src="//rf.revolvermaps.com/0/0/8.js?i=&amp;m=0&amp;s=220&amp;c=ff0000&amp;cr1=ffffff&amp;f=arial&amp;l=33&amp;bv=35" async="async"></script>
</div>

    </section>
    
  </div>
</aside>

      </div>
    </main>
   
    <footer id="footer" class="footer">
      <div class="footer-inner">
        <div class="copyright" >
  <span itemprop="copyrightYear">  &copy; 
  2013 - 2023</span>
  <span class="with-love"><i class="fa fa-heart"></i></span>
  <span class="author" itemprop="copyrightHolder">天地维杰网</span>
  <span class="icp" itemprop="copyrightHolder"><a href="https://beian.miit.gov.cn/" target="_blank">京ICP备13019191号-1</a></span>
</div>
<div class="powered-by">
  Powered by - <a class="theme-link" href="http://gohugo.io" target="_blank" title="hugo" >Hugo v0.63.2</a>
</div>
<div class="theme-info">
  Theme by - <a class="theme-link" href="https://github.com/xtfly/hugo-theme-next" target="_blank"> NexT
  </a>
</div>


      </div>
    </footer>

    <div class="back-to-top">
      <i class="fa fa-arrow-up"></i>
      <span id="scrollpercent"><span>0</span>%</span>
    </div>
  </div>

  

<script type="text/javascript">
  if (Object.prototype.toString.call(window.Promise) !== '[object Function]') {
    window.Promise = null;
  }
</script>
<script type="text/javascript" src="http://www.shutdown.cn/js/vendor/jquery/index.js?v=2.1.3"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/vendor/fastclick/lib/fastclick.min.js?v=1.0.6"></script> 
<script type="text/javascript" src="http://www.shutdown.cn/js/vendor/jquery_lazyload/jquery.lazyload.js?v=1.9.7"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/vendor/velocity/velocity.min.js?v=1.2.1"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/vendor/velocity/velocity.ui.min.js?v=1.2.1"></script>
<script src="http://www.shutdown.cn/js/vendor/ua-parser-js/dist/ua-parser.min.js?v=0.7.9"></script>

<script src="http://www.shutdown.cn/js/vendor/fancybox/jquery.fancybox.pack.js?v=2.1.5"></script>

<script type="text/javascript" src="http://www.shutdown.cn/js/utils.js"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/motion.js"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/affix.js"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/schemes/pisces.js"></script>

<script type="text/javascript" src="http://www.shutdown.cn/js/scrollspy.js"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/post-details.js"></script>
<script type="text/javascript" src="http://www.shutdown.cn/js/toc.js"></script>

<script type="text/javascript" src="http://www.shutdown.cn/js/bootstrap.js"></script>

<script type="text/javascript" src="http://www.shutdown.cn/js/search.js"></script>
<script type="text/x-mathjax-config">
  MathJax.Hub.Config({
    extensions: ["tex2jax.js"],
    jax: ["input/TeX", "output/HTML-CSS"],
    tex2jax: {
      inlineMath: [ ['$','$'] ],
      displayMath: [ ['$$','$$'] ],
      processEscapes: true
    },
    "HTML-CSS": { fonts: ["TeX"] }
  });
</script>
<script src='https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/MathJax.js?config=TeX-AMS-MML_HTMLorMML' async></script>
</body>
</html>